Capturing and displaying images with multiple focal planes

ABSTRACT

The present disclosure generally relates to capturing and displaying video with multiple focal planes. The video includes a subject with a predefined portion of the subject identified in a first focal region. When a set of one or more conditions is met, the video is displayed with a focal plane of the video selected to be outside of the first focal region. When the set of one or more conditions is met is no longer met; and the video is displayed with the focal plane of the video selected to be inside of the first focal region.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/528,941, filed Aug. 1, 2019, entitled “CAPTURING AND DISPLAYINGIMAGES WITH MULTIPLE FOCAL PLANES”, which claims priority to U.S.Provisional Application No. 62/739,093, filed Sep. 28, 2018, entitled“CAPTURING AND DISPLAYING IMAGES WITH MULTIPLE FOCAL PLANES”, thecontents of which are hereby incorporated by reference in theirentireties.

FIELD

The present disclosure relates generally to user interfaces, and morespecifically to techniques for capturing and displaying images withmultiple focal planes.

BACKGROUND

Users are increasingly using electronic devices to capture images andvirtually communicate with others for personal and business reasons.Most electronic devices are capable of capturing images for livecommunication between users. As an example, some electronic devicesprovide interactive interfaces to display and control the livecommunication.

BRIEF SUMMARY

Some techniques for capturing and displaying images, however, aregenerally cumbersome and inefficient. For example, some existingtechniques use a complex and time-consuming user interface to capture ordisplay images with different focal planes, which may include multiplekey presses or other physical inputs. Existing techniques require moretime than necessary, wasting user time and device energy. This latterconsideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for capturing anddisplaying images with multiple focal planes. Such methods andinterfaces optionally complement or replace other methods for capturingand displaying images. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated computing devices, such methods and interfacesconserve power and increase the time between battery charges.

In some embodiments, a method is performed at an electronic device witha display. The method includes: displaying video for a livecommunication session, wherein the video includes a subject of the livecommunication session with a predefined portion of the subjectidentified in a first focal region, including, in accordance with adetermination that a set of one or more conditions is met, displayingthe video with a focal plane of the video selected to be outside of thefirst focal region; and while displaying the video for the livecommunication session with the focal plane of the video selected to beoutside of the first focal region, determining that the set of one ormore conditions is no longer met; and in response to the determinationthat the set of one or more conditions is no longer met, displaying thevideo for the live communication session with the focal plane of thevideo selected to be inside of the first focal region.

In some embodiments, a non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display. The one or moreprograms include instructions for: displaying video for a livecommunication session, wherein the video includes a subject of the livecommunication session with a predefined portion of the subjectidentified in a first focal region, including, in accordance with adetermination that a set of one or more conditions is met, displayingthe video with a focal plane of the video selected to be outside of thefirst focal region; and while displaying the video for the livecommunication session with the focal plane of the video selected to beoutside of the first focal region, determining that the set of one ormore conditions is no longer met; and in response to the determinationthat the set of one or more conditions is no longer met, displaying thevideo for the live communication session with the focal plane of thevideo selected to be inside of the first focal region.

In some embodiments, a transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display. The one or moreprograms include instructions for: displaying video for a livecommunication session, wherein the video includes a subject of the livecommunication session with a predefined portion of the subjectidentified in a first focal region, including, in accordance with adetermination that a set of one or more conditions is met, displayingthe video with a focal plane of the video selected to be outside of thefirst focal region; and while displaying the video for the livecommunication session with the focal plane of the video selected to beoutside of the first focal region, determining that the set of one ormore conditions is no longer met; and in response to the determinationthat the set of one or more conditions is no longer met, displaying thevideo for the live communication session with the focal plane of thevideo selected to be inside of the first focal region.

In some embodiments, an electronic device includes a display, one ormore processors, and memory. The memory stores one or more programsconfigured to be executed by the one or more processors. The one or moreprograms including instructions for: displaying video for a livecommunication session, wherein the video includes a subject of the livecommunication session with a predefined portion of the subjectidentified in a first focal region, including, in accordance with adetermination that a set of one or more conditions is met, displayingthe video with a focal plane of the video selected to be outside of thefirst focal region; and while displaying the video for the livecommunication session with the focal plane of the video selected to beoutside of the first focal region, determining that the set of one ormore conditions is no longer met; and in response to the determinationthat the set of one or more conditions is no longer met, displaying thevideo for the live communication session with the focal plane of thevideo selected to be inside of the first focal region.

In some embodiments, an electronic device includes: a display; means fordisplaying video for a live communication session, wherein the videoincludes a subject of the live communication session with a predefinedportion of the subject identified in a first focal region, including,means for, in accordance with a determination that a set of one or moreconditions is met, displaying the video with a focal plane of the videoselected to be outside of the first focal region; and means for, whiledisplaying the video for the live communication session with the focalplane of the video selected to be outside of the first focal region,determining that the set of one or more conditions is no longer met; andmeans for, in response to the determination that the set of one or moreconditions is no longer met, displaying the video for the livecommunication session with the focal plane of the video selected to beinside of the first focal region.

In some embodiments, a method is performed at an electronic device witha camera. The method includes: detecting activation of a shutter buttonthat is associated with capturing still images; and in response to theactivation of the shutter button, capturing a plurality of still imageswith a plurality of different focal planes, including: capturing firstimage data with the camera focused at a first focal plane; and aftercapturing the first image data with the camera focused at the firstfocal plane, capturing second image data with the camera focused at asecond focal plane, wherein the second focal plane is selected withoutreference to changes in objects in the field of view of the camerabetween the capture of the first image data and the capture of thesecond image data.

In some embodiments, a non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a camera. The one or moreprograms include instructions for: detecting activation of a shutterbutton that is associated with capturing still images; and in responseto the activation of the shutter button, capturing a plurality of stillimages with a plurality of different focal planes, including: capturingfirst image data with the camera focused at a first focal plane; andafter capturing the first image data with the camera focused at thefirst focal plane, capturing second image data with the camera focusedat a second focal plane, wherein the second focal plane is selectedwithout reference to changes in objects in the field of view of thecamera between the capture of the first image data and the capture ofthe second image data.

In some embodiments, a transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a camera. The one or moreprograms include instructions for: detecting activation of a shutterbutton that is associated with capturing still images; and in responseto the activation of the shutter button, capturing a plurality of stillimages with a plurality of different focal planes, including: capturingfirst image data with the camera focused at a first focal plane; andafter capturing the first image data with the camera focused at thefirst focal plane, capturing second image data with the camera focusedat a second focal plane, wherein the second focal plane is selectedwithout reference to changes in objects in the field of view of thecamera between the capture of the first image data and the capture ofthe second image data.

In some embodiments, an electronic device includes a camera, one or moreprocessors, and memory. The memory stores one or more programsconfigured to be executed by the one or more processors. The one or moreprograms including instructions for: detecting activation of a shutterbutton that is associated with capturing still images; and in responseto the activation of the shutter button, capturing a plurality of stillimages with a plurality of different focal planes, including: capturingfirst image data with the camera focused at a first focal plane; andafter capturing the first image data with the camera focused at thefirst focal plane, capturing second image data with the camera focusedat a second focal plane, wherein the second focal plane is selectedwithout reference to changes in objects in the field of view of thecamera between the capture of the first image data and the capture ofthe second image data.

In some embodiments, an electronic device includes: a camera; means fordetecting activation of a shutter button that is associated withcapturing still images; and means for, in response to the activation ofthe shutter button, capturing a plurality of still images with aplurality of different focal planes, including: means for capturingfirst image data with the camera focused at a first focal plane; andmeans for after capturing the first image data with the camera focusedat the first focal plane, capturing second image data with the camerafocused at a second focal plane, wherein the second focal plane isselected without reference to changes in objects in the field of view ofthe camera between the capture of the first image data and the captureof the second image data.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for capturing and displaying images with multiple focalplanes, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for capturing and displaying images.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6H illustrate exemplary user interfaces displaying video for alive communication session with multiple focal planes, in accordancewith some embodiments.

FIGS. 7A-7B are a flow diagram illustrating a method for displayingvideo for a live communication session with different focal planes, inaccordance with some embodiments.

FIGS. 8A-8E illustrate exemplary user interfaces for capturing imageswith multiple focal planes, in accordance with some embodiments.

FIG. 9 is a flow diagram illustrating a method for displaying capturinga plurality of still images with a plurality of different focal planes,in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for capturing and displaying images with multiple focalplanes. Such techniques can reduce the cognitive burden on a user whoparticipates in live communication sessions or edits images, therebyenhancing productivity. Further, such techniques can reduce processorand battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for capturing anddisplaying images with multiple focal planes. FIGS. 6A-6H illustrateexemplary user interfaces for displaying video for a live communicationsession with multiple focal planes. FIGS. 7A-7B are a flow diagramillustrating methods of displaying the video for the live communicationsession in accordance with some embodiments. The user interfaces inFIGS. 6A-6H are used to illustrate the processes described below,including the processes in FIGS. 7A-7B. FIGS. 8A-8E illustrate exemplaryuser interfaces for capturing images with multiple focal planes. FIG. 9is a flow diagram illustrating methods of capturing the images inaccordance with some embodiments. The user interfaces in FIGS. 8A-8E areused to illustrate the processes described below, including theprocesses in FIG. 9 .

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2 ) optionally include an up/downbutton for volume control of speaker 111 and/or microphone 113. The oneor more buttons optionally include a push button (e.g., 206, FIG. 2 ).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

In some embodiments, a depth map (e.g., depth map image) containsinformation (e.g., values) that relates to the distance of objects in ascene from a viewpoint (e.g., a camera, an optical sensor, a depthcamera sensor). In one embodiment of a depth map, each depth pixeldefines the position in the viewpoint's Z-axis where its correspondingtwo-dimensional pixel is located. In some embodiments, a depth map iscomposed of pixels wherein each pixel is defined by a value (e.g.,0-255). For example, the “0” value represents pixels that are located atthe most distant place in a “three dimensional” scene and the “255”value represents pixels that are located closest to a viewpoint (e.g., acamera, an optical sensor, a depth camera sensor) in the “threedimensional” scene. In other embodiments, a depth map represents thedistance between an object in a scene and the plane of the viewpoint. Insome embodiments, the depth map includes information about the relativedepth of various features of an object of interest in view of the depthcamera (e.g., the relative depth of eyes, nose, mouth, ears of a user'sface). In some embodiments, the depth map includes information thatenables the device to determine contours of the object of interest in az direction.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700 and900 (FIGS. 7A-7B and 9 ). A computer-readable storage medium can be anymedium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “ITL”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“ITS”) in FIG. 5H. The gesture performed with contact 562 is detected ontouch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “ITD”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “ITD”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “ITD”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6H illustrate exemplary user interfaces displaying video for alive communication session with multiple focal planes, in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 7A-7B.

FIG. 6A illustrates a first device 600 a with first touch-sensitivedisplay 602 a. In some embodiments, first device 600 a includes one ormore features of devices 100, 300, and 500. First device 600 a alsoincludes first camera 603 a, which, at a minimum, includes an imagesensor that is capable of capturing data representing a portion of thelight spectrum (e.g., visible light, infrared light, or ultravioletlight). First camera 603 a includes at least one focal lens capable ofbeing adjusted to focus first camera 603 a on different focal planes(e.g., distances from first camera 603 a at which the sharpest focus isattained). In some embodiments, first camera 603 a includes a singlefocal lens for adjusting the focal plane. In some embodiments, the focalplane is adjusted by modifying the shape of the single focal lens. Firstcamera 603 a is capable of being adjusted to focus on different focalplanes and capture images at different focal planes within a briefamount of time (e.g., less than 0.5 ms, 1 ms, 5 ms, 10 ms, 15 ms, or 20ms). The images are captured at each of the different focal planes at aspeed such that the multiple images with different focal planes can beassociated with a single frame of video (e.g., the images are capturedwithin a time period less than the time period of a frame of video). Thecontent of the images associated with a frame of video appearssubstantially the same except for the difference in focal planes betweenthe images. In some embodiments, one or more photographic properties offirst camera 603 a other than the focal plane (e.g., exposure, zoomlevel, white balance, contrast, ISO value) are kept constant during thecapture of the multiple images.

In some embodiments, first camera 603 a includes multiple image sensorsand/or other types of sensors. In addition to capturing datarepresenting sensed light, in some embodiments, first camera 603 a iscapable of capturing other types of data, such as depth data. Forexample, in some embodiments, first camera 603 a also captures depthdata using techniques based on speckle, time-of-flight, parallax, orfocus. Image data that first device 600 a captures using first camera603 a includes data corresponding to a portion of the light spectrum fora scene within the field of view of the camera. Additionally, in someembodiments, the captured image data also includes depth data for thelight data. In some other embodiments, the captured image data containsdata sufficient to determine or generate depth data for the data for theportion of the light spectrum.

In some examples, first device 600 a includes a depth camera (e.g., aspart of first camera 603 a), such as an infrared camera, a thermographiccamera, or a combination thereof. In some examples, first device 600 afurther includes a light-emitting device (e.g., light projector), suchas an IR flood light, a structured light projector, or a combinationthereof. The light-emitting device is, optionally, used to illuminatethe subject during capture of the image by a visible light camera and adepth camera (e.g., an IR camera) and the information from the depthcamera and the visible light camera are used to determine a depth map ofdifferent portions of a subject captured by the visible light camera. Insome embodiments, a depth map (e.g., depth map image) containsinformation (e.g., values) that relates to the distance of objects in ascene from a viewpoint (e.g., a camera). In one embodiment of a depthmap, each depth pixel defines the position in the viewpoint's Z-axiswhere its corresponding two-dimensional pixel is located. In someexamples, a depth map is composed of pixels wherein each pixel isdefined by a value (e.g., 0-255). For example, the “0” value representspixels that are located at the most distant place in a “threedimensional” scene and the “255” value represents pixels that arelocated closest to a viewpoint (e.g., camera) in the “three dimensional”scene. In other examples, a depth map represents the distance between anobject in a scene and the plane of the viewpoint.) In some embodiments,the depth map includes information about the relative depth of variousfeatures of an object of interest in view of the depth camera (e.g., therelative depth of eyes, nose, mouth, ears of a user's face). In someembodiments, the depth map includes information that enables the deviceto determine contours of the object of interest in a z direction.

As illustrated in FIG. 6A, first device 600 a displays outgoingnotification 604 of a live communication application (e.g., a video chatapplication). The outgoing notification 604 is displayed in response tosending a request to a second device (e.g., second device 600 bdescribed in reference to FIG. 6B) to join a live communication session(e.g., a video chat). Outgoing notification 604 includes cancelaffordance 606 for canceling the request to join the live communicationsession (e.g., to immediately end the live communication session). Insome embodiments, outgoing notification 604 also includes a name 608 ofa second participant being requested to join the live communicationsession and/or an avatar 610 for the second participant. Outgoingnotification 604 also includes an image 612 (e.g., a frame of video) ofthe first participant sending the request (e.g., a user of first device600 a) (e.g., as a preview of video being sent to second device 600 b,as described in reference to FIG. 6B). Image 612 is captured via firstcamera 603 a and corresponds to an environment within the field-of-viewof first camera 603 a. In this example, the environment within thefield-of-view of first camera 603 a includes the first participantsending the request.

In some embodiments, first device 600 a captures image 612 such that thefirst participant appears out-of-focus (as illustrated by the dashedlines shown in FIG. 6A). In some embodiments, first device 600 aidentifies a first focal region where a predefined portion of the firstparticipant (e.g., the first participant's face) would be captured witha sharp focus, and sets a focal plane of first camera 603 a to beoutside of that first focal region (e.g., the focal plane of firstcamera 603 a is set such that the first participant's face is capturedout-of-focus). In some embodiments, first device 600 a captures multipleimages of the first participant, where each image is captured with thefirst camera 603 a set to a different focal plane, and where at leastone of the images is captured with the focal plane of first camera 603 aset to be outside of the first focal region (e.g., the firstparticipant's face is captured out-of-focus in at least one of theimages). In some embodiments, one or more of the images captured byfirst camera 603 a are transmitted to the second device with the requestto join the live communication session.

FIG. 6B illustrates a second device 600 b with second touch-sensitivedisplay 602 b. In some embodiments, second device 600 b includes one ormore features of devices 100, 300, 500, and 600 a. In some embodiments,second device 600 b also includes second camera 603 b. In someembodiments, second camera 603 b includes one or more features of firstcamera 600 a (e.g., at least one focal lens capable of being adjusted tofocus second camera 603 b on different focal planes).

As illustrated in FIG. 6B, second device 600 b displays incomingnotification 614 of a live communication application (e.g., a video chatapplication, such as a video chat application that is the same as, orcompatible with, the video chat application generating notificationoutgoing notification 604 on device 600 a). Incoming notification 614 isdisplayed in response to receiving a request to join a livecommunication session (e.g., a video chat) from first device 600 a.Incoming notification 614 includes answer affordance 616 for joining thelive communication session (e.g., to immediately join the livecommunication session or display a menu with options for joining thelive communication session). In some embodiments, incoming notification614 also includes a name 618 of the first participant sending therequest and/or an avatar 620 for the first participant. Incomingnotification 614 also includes an image 622 (e.g., a frame of video) ofthe first participant (e.g., the user of first device 600 a).

While the request to join the live communication session is pending(e.g., before answer affordance 616 is selected), image 622 is displayedsuch that the first participant sending the request appears out-of-focus(e.g., blurry). In some embodiments, the first participant is displayedout-of-focus as a result of first device 600 a setting the focal planeof first camera 603 a to a focal region where the first participant isout-of-focus. In some embodiments, the participant is displayedout-of-focus as a result of second device 600 b sending a request tofirst device 600 a to set the focal plane of first camera 603 a to afocal region where the first participant is out-of-focus. In someembodiments, the video data being sent by first device 600 a to seconddevice 600 b includes image data of the first participant at multiplefocal planes. Second device 600 b then selects image data with a focalplane where the first participant is out-of-focus for display as image622 in the incoming notification 614.

As illustrated in FIG. 6C, while the request to join the livecommunication session continues to be pending, image 622 is displayed bysecond device 600 b such that the first participant continues to appearout-of-focus after the distance of the first participant from firstcamera 600 a changes (e.g., the first participant moves closer to orfurther away from first camera 600 a capturing image 622). In someembodiments, as first device 600 a detects that the distance of thefirst participant from first camera 600 a is changing, first device 600a modifies the focal plane of first camera 603 a such that the firstparticipant remains out-of-focus. In some embodiments, second device 600b detects that the distance of the first participant from the firstcamera 603 a is changing, and sends a request to first device 600 a tomodify the focal plane of first camera 603 a to keep the firstparticipant out-of-focus. In some embodiments, the video data being sentby first device 600 a to second device 600 b includes image data of thefirst participant at multiple focal planes. Second device 600 b thenselects image data with a focal plane where the first participant isout-of-focus for display as the participant moves closer to or furtheraway from first camera 603 a.

In some embodiments, the live communication session is accepted inresponse to an input 617 (e.g., a contact on second touch-sensitivedisplay 602 b) on answer affordance 616. In response to second device600 b accepting the request to join the live communication session,image 622 changes to display the first participant in-focus (e.g., thefirst participant's face appears sharp), as shown in FIG. 6D.

FIG. 6D illustrates second device 600 b displaying live communicationinterface 624 on second touch-sensitive display 602 b. Livecommunication interface 624 is displayed in response to an acceptance(e.g., input 617) of the request to join the live communication sessionsent by first device 600 a. In response to second device 600 b joiningthe live communication session, image 622 changes to display the firstparticipant in-focus (e.g., the first participant's face appears sharp,as illustrated by the solid lines in FIG. 6D). Live communicationinterface 624 further includes a preview image 626 of the secondparticipant.

In some embodiments, in response to second device 600 b accepting therequest to join the live communication session, first device 600 a setsthe focal plane of first camera 603 a such that the first participant iscaptured in-focus. In some embodiments, first device 600 a sets thefocal plane in response to a request from second device 600 b. Videodata with the first participant captured in-focus is then transmitted tosecond device 600 b for display as image 622 in live communicationinterface 624. In some embodiments, first device 600 a captures multipleimages of the first participant, where each image is captured with thefirst camera 603 a set to a different focal plane, and where at leastone of the images is captured with the focal plane of first camera 603 aset to capture the first participant in-focus. The images of the firstparticipant captured at different focal planes are transmitted to seconddevice 600 b, and second device 600 b selects image 622 where the firstparticipant is captured in-focus for display in the live communicationinterface 624.

As illustrated in FIG. 6E, after the request to join the livecommunication session has been accepted, image 622 is displayed bysecond device 600 b such that the first participant continues to appearin-focus after the distance of the first participant from first camera600 a changes (e.g., the first participant moves closer or further awayfrom first camera 600 a capturing image 622). In some embodiments, asfirst device 600 a detects that the distance of the first participantfrom first camera 600 a is changing, first device 600 a modifies thefocal plane of first camera 603 a such that the first participantremains in-focus. In some embodiments, second device 600 b detects thatthe distance of the first participant from the first camera 603 a ischanging, and sends a request to first device 600 a to modify the focalplane of first camera 603 a to keep the first participant in-focus. Insome embodiments, first device 600 a captures multiple images of thefirst participant, where each image is captured with the first camera603 a set to a different focal plane, and where at least one of theimages is captured with the focal plane of first camera 603 a set tocapture the first participant in-focus at the changed distance fromfirst camera 603 a. The images of the first participant captured atdifferent focal planes are transmitted to second device 600 b, andsecond device 600 b selects image 622 where the first participant iscaptured in-focus at the changed distance from first camera 603 a fordisplay in the live communication interface 624.

As illustrated in FIG. 6F, after the request to join the livecommunication session has been accepted, the first participant partiallyexits the frame of first camera 603 a (as shown in FIG. 6A). When thefirst participant partially exits the camera frame (e.g., at least aportion of the first participant's face is out of view of first camera603 a), a lack of attention is detected. In response to detecting thelack of attention, image 622 is displayed by second device 600 b suchthat the first participant appears out-of-focus. In some embodiments,the lack of attention is detected by first device 600 a, and then firstdevice 600 a modifies the focal plane of first camera 603 a such thatthe first participant appears out-of-focus. In some embodiments, thelack of attention is detected by second device 600 b, and then seconddevice 600 b sends a request to first device 600 a to modify the focalplane of first camera 603 a to capture the first participantout-of-focus. In some embodiments, first device 600 a captures multipleimages of the first participant, where each image is captured with thefirst camera 603 a set to a different focal plane, and where at leastone of the images is captured with the focal plane of first camera 603 aset to capture the first participant out-of-focus. The images of thefirst participant captured at different focal planes are transmitted tosecond device 600 b, and second device 600 b selects image 622 where thefirst participant is captured out-of-focus for display in the livecommunication interface 624 when the lack of attention is detected.

When the first participant returns to the camera frame (e.g., the firstparticipant's face is fully in view of first camera 603 a), a return ofattention is detected. In response to the return of attention, image 622is displayed by second device 600 b such that the first participantappears in-focus again, as shown in FIG. 6D. In some embodiments, thereturn of attention is detected by first device 600 a, and then firstdevice 600 a modifies the focal plane of first camera 603 a such thatthe first participant appears in-focus. In some embodiments, the returnof attention is detected by second device 600 b, and then second device600 b sends a request to first device 600 a to modify the focal plane offirst camera 603 a to capture the first participant in-focus. In someembodiments, first device 600 a captures multiple images of the firstparticipant, where each image is captured with the first camera 603 aset to a different focal plane, and where at least one of the images iscaptured with the focal plane of first camera 603 a set to capture thefirst participant in-focus. The images of the first participant capturedat different focal planes are transmitted to second device 600 b, andsecond device 600 b selects image 622 where the first participant iscaptured in-focus for display in the live communication interface 624when the return of attention is detected.

As illustrated in FIG. 6G, after the request to join the livecommunication session has been accepted, the first participant looksaway from first device 600 a (as shown in FIG. 6A) (e.g., the firstparticipant turns their head away from first device 600 a or the firstparticipant's eyes gaze in a direction other than toward first device600 a). When the first participant looks away from first device 600 a, alack of attention is detected. In response to detecting the lack ofattention, image 622 is displayed by second device 600 b such that thefirst participant appears out-of-focus. In some embodiments, the lack ofattention is detected by first device 600 a, and then first device 600 amodifies the focal plane of first camera 603 a such that the firstparticipant appears out-of-focus. In some embodiments, the lack ofattention is detected by second device 600 b, and then second device 600b sends a request to first device 600 a to modify the focal plane offirst camera 603 a to capture the first participant out-of-focus. Insome embodiments, first device 600 a captures multiple images of thefirst participant, where each image is captured with the first camera603 a set to a different focal plane, and where at least one of theimages is captured with the focal plane of first camera 603 a set tocapture the first participant out-of-focus. The images of the firstparticipant captured at different focal planes are transmitted to seconddevice 600 b, and second device 600 b selects image 622 where the firstparticipant is captured out-of-focus for display in the livecommunication interface 624 when the lack of attention is detected.

When the first participant looks back toward first device 600 a (e.g.,the first participant turns their head toward first device 600 a or thefirst participant's eyes gaze in a direction toward first device 600 a),a return of attention is detected. In response to the return ofattention, image 622 is displayed by second device 600 b such that thefirst participant appears in-focus again, as shown in FIG. 6D. In someembodiments, the return of attention is detected by first device 600 a,and then first device 600 a modifies the focal plane of first camera 603a such that the first participant appears in-focus. In some embodiments,the return of attention is detected by second device 600 b, and thensecond device 600 b sends a request to first device 600 a to modify thefocal plane of first camera 603 a to capture the first participantin-focus. In some embodiments, first device 600 a captures multipleimages of the first participant, where each image is captured with thefirst camera 603 a set to a different focal plane, and where at leastone of the images is captured with the focal plane of first camera 603 aset to capture the first participant in-focus. The images of the firstparticipant captured at different focal planes are transmitted to seconddevice 600 b, and second device 600 b selects image 622 where the firstparticipant is captured in-focus for display in the live communicationinterface 624 when the return of attention is detected.

As illustrated in FIG. 6H, in response to an input 628 (e.g., a contacton second touch-sensitive display 602 b), the focal plane of image 622is modified. In some embodiments, in response to input 628, non-visualfeedback (e.g., audio/tactile) is provided in conjunction with (e.g., atthe same time or near the same time as) modifying the focal plane ofimage 622.

In some embodiments, the focal plane of image 622 is modified inresponse to input 628 being on a location of image 622 having adifferent depth (e.g., the location of an object in the background ofimage 622). In response to input 628, second device 600 b displays image622 such that a portion of the image at the location selected with input628 is displayed in-focus (e.g., the focal plane is changed tocorrespond to the background object). In some examples, as a result ofchanging the focal plane, first participant is displayed out-of-focus inimage 622. In some embodiments, second device 600 b sends a request tofirst device 600 a to modify the focal plane of first camera 603 a tocapture the portion of the image at the location selected with input 628in-focus. In some embodiments, first device 600 a captures multipleimages with different focal planes. The multiple images are transmittedto second device 600 b, and second device 600 b selects image 622 wherethe portion of the image at the location selected with input 628 iscaptured in-focus for display in the live communication interface 624.

In some embodiments, the focal plane of image 622 is modified based on acharacteristic intensity of input 628 (e.g., a contact on secondtouch-sensitive display 602 b having a characteristic intensity). Forexample, an input 628 having a characteristic intensity at or below thelight press intensity threshold changes the focal plane of image 622 tocorrespond to a minimum focal plane of first camera 603 a (e.g., ashallow focal plane where objects near first camera 603 a are displayedin-focus). As the characteristic intensity of input 628 increases, thefocal plane of image 622 is changed to correspond to deeper focal planesof first camera 603 a (e.g., the focal planes shift further away fromfirst camera 603 a as the characteristic intensity of input 628increases). In this way, a user can vary the focal plane of image 622 bychanging the characteristic intensity of input 628.

In some embodiments, the focal plane of image 622 is modified based on aduration of input 628 (e.g., the length of time a contact is held onsecond touch-sensitive display 602 b). For example, when input 628 isinitially detected on second touch-sensitive display 602 b, the focalplane of image 622 is changed to correspond to a minimum focal plane offirst camera 603 a (e.g., a shallow focal plane where objects near firstcamera 603 a are displayed in-focus). As the duration of input 628increases, the focal plane of image 622 is changed to correspond todeeper focal planes of first camera 603 a (e.g., the focal planesgradually shift further away from first camera 603 a as the duration ofthe contact increases). When input 628 ceases to be detected, the focalplane of image 622 is maintained at the last focal plane displayed forimage 622. In this way, a user can vary the focal plane of image 622 bychanging the duration of input 628.

FIGS. 7A-7B are a flow diagram illustrating a method for displayingvideo for a live communication session with different focal planes, inaccordance with some embodiments. Method 700 is performed at a device(e.g., 100, 300, 500, 600 b) with a display. Some operations in method700 are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 700 provides, among other things, anintuitive way for displaying video for a live communication session. Themethod reduces the cognitive burden on a user viewing the livecommunication session, thereby creating a more efficient human-machineinterface.

The device (e.g., second device 600 b) displays (702) video for a livecommunication session (e.g., an audio/video communication session with alive data stream transmitted by a capture device (e.g. first device 600a)). The video includes a subject of the live communication session witha predefined portion of the subject identified in a first focal region(e.g., a focal region where the head or face of a participant of thelive communication session is in focus). In some embodiments, the videofor the live communication session includes first image datacorresponding to a focal plane outside of the first focal region andsecond image data corresponding to a focal plane inside the first focalregion (e.g., video data stream from first device 600 a includes datafor multiple focal depths). In some embodiments, the first image dataand second image data are transmitted/received at different periods oftime in the video data, or at the same (e.g., approximately the same)period of time (e.g. the video data includes two discretechannels/streams of data for the same time period, having differentfocal planes). In some embodiments, the device (e.g., second device 600b) selects the image data with the focal plane outside the first focalregion (e.g., to display the subject out-of-focus).

In accordance with a determination that a set of one or more conditionsis met, the device displays (704) the video with a focal plane of thevideo selected to be outside of the first focal region (e.g., thehead/face of a participant of the live communication session is out offocus in the video). In some embodiments, the video is captured by acapture device (e.g., first device 600 a) with a lens set outside thefirst focal region. In some embodiments, the video includes video dataat multiple focal depths and the device (e.g., second device 600 b)selects the video data with a focal plane outside the first focal regionfor display. Displaying video for a live communication session with thefocal plane of the video selected to be at different focal regions basedon whether one or more conditions are met improves visual feedback byenabling a user to quickly and easily recognize the status of the livecommunication session (e.g., whether the live communication session hasbeen joined and/or whether another participant is engaged in the livecommunication session). Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the video for the live communication session iscaptured by a camera of a capture device (e.g., first device 600 a withfirst camera 603 a), and in accordance with the determination that theset of one or more conditions is met, the focal plane of the camera hasbeen set (e.g. mechanically set/adjusted, set/adjusted via software)outside of the first focal region. In some embodiments, the device(e.g., second device 600 b) sends a request to the capture device (e.g.,first device 600 a) to set the focal plane of the camera (e.g., firstcamera 603 a) of the capture device outside of the first focal region.

Optionally, while (710) displaying the video for the live communicationsession with the focal plane of the video selected to be outside of thefirst focal region and while the set of one or more conditions is met,the device (e.g., second device 600 b) detects (712) a change inposition of the predefined portion of the subject (e.g., the head/faceof the participant moves forward or backward). The device then modifies(714) the first focal region based on the change in position of thepredefined portion of the subject. The device then displays (716) thevideo for the live communication session with the focal plane of thevideo adjusted to continue being outside of the first focal region(e.g., the focal plane is changed to keep the head/face of theparticipant out-of-focus). Continually changing the focal plane for thelive communication session to be outside of a focal region of thesubject as the subject changes position improves visual feedback byenabling a user to quickly and easily recognize the status of the livecommunication session as the subject moves. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

While displaying the video for the live communication session with thefocal plane of the video selected to be outside of the first focalregion, the device determines (706) that the set of one or moreconditions is no longer met.

In response to the determination that the set of one or more conditionsis no longer met, the device displays (708) the video for the livecommunication session with the focal plane of the video selected to beinside of the first focal region (e.g., a focal region where thehead/face of the participant of the live communication session is nolonger out of focus in the video). In some embodiments, the video iscaptured by another device (e.g., first device 600 a) with a camera lensset at a focal plane inside the first focal region. In some embodiments,the video includes video data at multiple focal depths and the device(e.g., second device 600 b) selects the video data with a focal planeinside the first focal region for display.

Optionally, while (718) the set of one or more conditions is no longermet and while displaying the video for the live communication sessionwith the focal plane of the video selected to be inside of the firstfocal region, the device (e.g., second device 600 b) detects (720) achange in position of the predefined portion of the subject (e.g., thehead/face of the participant moves forward or backward). The device thenmodifies (722) the first focal region based on the change in position ofthe predefined portion of the subject. The device then displays (724)the video for the live communication session with the focal plane of thevideo adjusted to continue being inside the first focal region (e.g.,the focal plane is changed to keep the head/face of the participantin-focus). Continually changing the focal plane for the livecommunication session to be inside of a focal region of the subject asthe subject changes position improves visual feedback by enabling a userto quickly and easily recognize the status of the live communicationsession as the subject moves. Providing improved visual feedback to theuser enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the device (e.g., second device 600 b) receives arequest to participate in the live communication session, and the set ofone or more conditions includes a condition that is met while therequest is pending (e.g., when receiving an incoming video call, videoof the participant initiating the call is displayed with theparticipant's head/face out-of-focus). In some embodiments, the requestis pending when the request remains unaccepted (e.g., the devicereceiving the request is not transmitting video back to the requestingdevice). In some embodiments, in response to detecting an acceptance(e.g., 617) of the request to participate in the live communicationsession (e.g., an input (e.g., a finger contact) on an acceptanceaffordance (e.g., 616) displayed on a touch-sensitive display), thedevice determines that the set of one or more conditions is no longermet (e.g., the subject is displayed out-of-focus until the livecommunication session is accepted, and then the subject is displayedin-focus). Displaying video for a live communication session with thefocal plane of the video selected to be at different focal regions basedon whether a request to join the live communication session is pendingimproves visual feedback by enabling a user to quickly and easilyrecognize the status of the live communication session. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the set of one or more conditions includes acondition that is met when a lack of attention from the subject of thelive communication session has been detected (e.g., subject of videocall appears out-of-focus when they are not paying attention to thevideo call) (e.g. detected via face and/or gaze detection techniquesthat are, optionally, based on analysis of the video data (e.g.,analysis performed at second device 600 b, or analysis performed byfirst device 600 a providing the video data along with attentiondetection data, to the second device 600 b)). In some embodiments, thelack of attention is detected based at least in part on the predefinedportion of the subject (e.g., the subject's head/face) at leastpartially exiting an image boundary of the live communication session(e.g., the camera frame of the capture device) for a predeterminedamount of time. In some embodiments, in response to a detection that thepredefined portion of the subject (e.g., the subject's head/face)reenters the image boundary of the live communication session (e.g., thecamera frame of the capture device), the device determines that the setof one or more conditions is no longer met (e.g., the subject isdisplayed out-of-focus if their head/face partially moves out of thecamera frame, and then the subject is displayed in-focus when theirhead/face returns to the camera frame). Displaying video for a livecommunication session with the focal plane of the video selected to beat different focal regions based on whether a lack of attention isdetected improves visual feedback by enabling a user to quickly andeasily recognize the status of the live communication session.Displaying video for the live communication session with the focal planeof the video selected to be at different focal regions based on whethera lack of attention is detected also improves privacy by obfuscating theidentity and/or activities of a participant when they are not payingattention to the live communication session. Providing improved visualfeedback and privacy to the user enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. Furthermore, user inputsare not required to change the focal plane of the video for the livecommunication, which allows the live communication session to quicklyand easily continue when a return of attention is detected. Performingan optimized operation without requiring further user input enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the lack of attention is detected based at least inpart on an eye gaze of the subject being directed in a direction otherthan toward a capture device (e.g., first device 600 a) capturing thelive communication session for a predetermined amount of time (e.g., thesubject is displayed out-of-focus while they look away from the firstcamera 603 a). In some embodiments, the subject's head/face remains inthe camera frame at the same focal plane while they look away from thecapture device. In some embodiments, in response to a detection that theeye gaze of the subject is directed toward the capture device (e.g.,first device 600 a) capturing the live communication session, the device(e.g., second device 600 b) determines that the set of one or moreconditions is no longer met (e.g., the subject is displayed out-of-focuswhile they look away from first camera 603 a, and then the subject isdisplayed in-focus when their gaze returns to first camera 603 a).Displaying video for a live communication session with the focal planeof the video selected to be at different focal regions based on aparticipant's eye gaze improves visual feedback by enabling a user toquickly and easily recognize the status of the live communicationsession. Displaying video for the live communication session with thefocal plane of the video selected to be at different focal regions basedon a participant's eye gaze also improves privacy by obfuscating theidentity and/or activities of a participant when they are not payingattention to the live communication session. Providing improved visualfeedback and privacy to the user enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. Furthermore, user inputsare not required to change the focal plane of the video for the livecommunication, which allows the live communication session to quicklyand easily continue when a return of attention is detected. Performingan optimized operation without requiring further user input enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

Optionally, while displaying the video for the live communicationsession on a touch-sensitive display, the device (e.g., second device600 b) detects (726) an input (e.g., 628) (e.g., a finger contact) onthe touch-sensitive display. The device then displays (728) the videofor the live communication session with the focal plane of the videoselected based on one or properties of the input (e.g., location,duration, and/or pressure of the finger contact).

In some embodiments, the device (e.g., second device 600 b) sends arequest to the capture device (e.g., first device 600 a) to set thefocal plane of the camera (e.g., first camera 603 a) based on the one ormore properties of the input (e.g., first device 600 a is instructed tocapture images having the desired focus, and to send video dataincluding the images to second device 600 b). In some embodiments, thevideo for the live communication session includes image data for two ormore focal planes (e.g., video stream from the first device 600 aincludes data for multiple focal depths (e.g., for the same time period(e.g., providing two channels of video data, having different focalplanes)), and the device (e.g., second device 600 b) selects image datahaving a respective focal plane of the two or more focal planes fordisplay based on the one or more properties of the input. In someembodiments, the one or more properties of the input includes acharacteristic intensity of the input. In some embodiments, the one ormore properties of the input includes a duration of the input (e.g.,long press). In some embodiments, the one or more properties of theinput includes a location of the input on the touch-sensitive display(e.g., if input location corresponds to a location of an object in thelive communication session, focal plane changes to a focal region of theobject). In some embodiments, the device (e.g., second device 600 b)provides non-visual feedback (e.g., audio/tactile) in conjunction with(e.g., at the same time or near the same time as) the video for the livecommunication session is displayed with the focal plane of the videoselected based on the one or properties of the input (e.g., non-visualfeedback occurs when the focal plane of the video changes in response tothe input).

Note that details of the processes described above with respect tomethod 700 (e.g., FIGS. 7A-7B) are also applicable in an analogousmanner to the methods described below. For example, method 700optionally includes one or more of the characteristics of the variousmethods described below with reference to method 900. For example, aplurality of still images with a plurality of different focal planes asdescribed below with respect to method 900 can used in a livecommunication session described above with respect to method 700. Forbrevity, these details are not repeated below.

FIGS. 8A-8E illustrate exemplary user interfaces for capturing imageswith multiple focal planes, in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 9 .

FIG. 8A illustrates a front-view 800 a and a rear-view 800 b of device800 with touch-sensitive display 802. In some embodiments, device 800includes one or more features of devices 100, 300, and 500. Device 800also includes an input device 804 (e.g., a mechanical input button, apress-able input button) and a camera 808. Camera 808, at a minimum,includes an image sensor that is capable of capturing data representinga portion of the light spectrum (e.g., visible light, infrared light, orultraviolet light). Camera 808 includes at least one focal lens capableof being adjusted to focus camera 808 on different focal planes (e.g.,distances from camera 808 at which the sharpest focus is attained). Insome embodiments, camera 808 includes a single focal lens for adjustingthe focal plane. In some embodiments, the focal plane is adjusted bymodifying the shape of the single focal lens. Camera 808 is capable ofbeing adjusted to focus on different focal planes and capture images ateach of the different focal planes within a brief amount of time (e.g.,less than 0.5 ms, 1 ms, 5 ms, 10 ms, 15 ms, or 20 ms). The images arecaptured at each of the different focal planes at a speed such that themultiple images with different focal planes can be associated withapproximately the same moment in time. The content of the images appearsubstantially the same except for the difference in focal planes betweenthe images. In some embodiments, one or more photographic properties ofcamera 808 other than the focal plane (e.g., exposure, zoom level, whitebalance, contrast, ISO value) are kept constant during the capture ofthe multiple images.

In some embodiments, camera 808 includes multiple image sensors and/orother types of sensors. In addition to capturing data representingsensed light, in some embodiments, camera 808 is capable of capturingother types of data, such as depth data. For example, in someembodiments, camera 808 also captures depth data using techniques basedon speckle, time-of-flight, parallax, or focus. Image data that device800 captures using camera 808 includes data corresponding to a portionof the light spectrum for a scene within the field of view of thecamera. Additionally, in some embodiments, the captured image data alsoincludes depth data for the light data. In some other embodiments, thecaptured image data contains data sufficient to determine or generatedepth data for the data for the portion of the light spectrum.

In some examples, device 800 includes a depth camera (e.g., as part ofcamera 808), such as an infrared camera, a thermographic camera, or acombination thereof. In some examples, camera 808 further includes alight-emitting device (e.g., light projector), such as an IR floodlight, a structured light projector, or a combination thereof. Thelight-emitting device is, optionally, used to illuminate the subjectduring capture of the image by a visible light camera and a depth camera(e.g., an IR camera) and the information from the depth camera and thevisible light camera are used to determine a depth map of differentportions of a subject captured by the visible light camera. In someembodiments, a depth map (e.g., depth map image) contains information(e.g., values) that relates to the distance of objects in a scene from aviewpoint (e.g., a camera). In one embodiment of a depth map, each depthpixel defines the position in the viewpoint's Z-axis where itscorresponding two-dimensional pixel is located. In some examples, adepth map is composed of pixels wherein each pixel is defined by a value(e.g., 0-255). For example, the “0” value represents pixels that arelocated at the most distant place in a “three dimensional” scene and the“255” value represents pixels that are located closest to a viewpoint(e.g., camera) in the “three dimensional” scene. In other examples, adepth map represents the distance between an object in a scene and theplane of the viewpoint.) In some embodiments, the depth map includesinformation about the relative depth of various features of an object ofinterest in view of the depth camera (e.g., the relative depth of eyes,nose, mouth, ears of a user's face). In some embodiments, the depth mapincludes information that enables the device to determine contours ofthe object of interest in a z direction.

In FIG. 8A, electronic device 800 displays, on touch-sensitive display802, a user interface 806 (e.g., a lock-screen user interface) thatincludes an affordance 812 for launching an image capture application(e.g., a camera application, an image/photo capturing and editingapplication). While displaying user interface 806, device 800 detects(e.g., via touch-sensitive display 802) an activation 801 of affordance812 (e.g., a tap gesture on affordance 812).

In FIG. 8B, in response to detecting activation 801 (or in response toother image capture requests), device 800 displays, on touch-sensitivedisplay 802, a user interface 814 of the image capture application. Inthis example, image capture application is in a photo mode. Whiledisplaying user interface 814 of the image capture application, device800 receives, via camera 808, image data corresponding to theenvironment within the field-of-view of camera 808.

Device 800 displays a preview image 818 corresponding to the image datareceived via camera 808 in the user interface 814 of the image captureapplication. In this example, preview image 818 includes multipleobjects, including a foreground object 820 a (e.g., a dog), amiddleground object (e.g., a person), and a background object 820 c(e.g., a plant). As illustrated in FIG. 8B, the focal plane of camera808 is set such that middlegound object 820 b and background object 820c are displayed out-of-focus (as illustrated by dashed lines) whileforeground object 820 a is displayed in-focus (as illustrated by solidlines) in preview image 818.

User interface 814 of the image capture application also includes ashutter affordance 822 (e.g., a virtual shutter button). Whiledisplaying preview image 818 in user interface 814, device 800 detectsan activation 805 of shutter affordance 822 (e.g., a single tap gestureon shutter affordance 822). In response to detecting activation 805,device 800 captures multiple still images corresponding to theenvironment currently in the field-of-view of camera 808 (e.g., multiplestill images of objects 820 a-820 c included in preview image 818). Thestill images are captured with multiple different focal planes inresponse to the activation 805. The multiple different focal planes areselected without reference to changes in objects in the field of view ofthe camera during the capture of the multiple still images (e.g., thedifferent focal planes are predefined or are selected at the same timeand do not change based on movement of the camera or movement of objectstoward or away from the camera during the capture of the multiple stillimages).

In some embodiments, the multiple still images are captured in responseto an activation of input device 804 (e.g., a single press of a physicalinput button). In some embodiments, after capturing the multiple stillimages with multiple different focal planes, the preview image 818continues to be displayed. In some embodiments, after capturing themultiple still images with multiple different focal planes, one of thecaptured still images corresponding to the preview image 818 isdisplayed (e.g., image 826 shown in FIG. 8D).

In some embodiments, device 800 detects an input 807 (e.g., a contact ontouch-sensitive display 802) at a location in preview image 818corresponding to middleground object 820 b. In response to detectinginput 807, device 800 captures multiple still images with differentfocal planes and then displays one of the captured still images (e.g.,image 824 shown in FIG. 8C) having a focal plane corresponding tomiddleground object 820 b, as shown in FIG. 8C (e.g., tapping on anobject in the preview image 818 causes multiple images with differentfocal planes to be captured, and an image with that object in-focus tobe displayed).

As illustrated in FIG. 8C, image 824 is displayed in user interface 814.Image 824 includes middleground object 820 b displayed in-focus, andforeground object 820 a and background object 820 c displayedout-of-focus. Image 824 is displayed in response to input 807 on thelocation in preview image 818 corresponding to middleground object 820b, as described in reference to FIG. 8B. While displaying image 824,device 800 detects input 809. In some embodiments, input 809 is at alocation in image 824 corresponding to foreground object 820 a. Inresponse to input 809 at the location corresponding to foreground object820 a, device 800 displays an image (e.g., image 826 shown in FIG. 8D)having a focal plane corresponding to foreground object 820 a, as shownin FIG. 8D (e.g., tapping on an object in image 824 causes an image tobe displayed with that object in-focus, without capturing additionalimages).

In some embodiments, input 809 has a corresponding characteristicintensity. Based on the characteristic intensity of input 809, device800 displays an image (e.g., image 826 shown in FIG. 8D) having adifferent focal plane (e.g., a light press causes an image with ashallow focal plane to be displayed, while a deep press causes an imagewith a deep focal plane to be displayed, without capturing additionalimages). In some embodiments, device 800 maintains display of image 824unless input 809 has a corresponding characteristic intensity greaterthan a threshold intensity. In some embodiments, the threshold intensityis based at least in part on a focal plane of an object captured in themultiple still images (e.g., the characteristic intensity of input 809pushes the focal plane deeper into image 824 until the focal plane is ata depth corresponding to an object in the image). When thecharacteristic intensity of input 809 is greater than the thresholdintensity, device 800 provides feedback indicating the thresholdintensity has been exceeded (e.g., audio/tactile/visual feedback occurswhen focal plane is pushed to a depth corresponding to an object in theimage).

In some embodiments, input 809 has a corresponding duration (e.g., along or short press). Based on the duration of input 809, device 800displays an image (e.g., image 826 shown in FIG. 8D) having a differentfocal plane (e.g., a short press causes an image with a shallow focalplane to be displayed, while a long press causes an image with a deepfocal plane to be displayed, without capturing additional images).

As illustrated in FIG. 8D, image 826 is displayed in user interface 814.Image 826 includes foreground object 820 a displayed in-focus, andmiddleground object 820 b and background object 820 c displayedout-of-focus. Image 826 is displayed in response to input 809, asdescribed in reference to FIG. 8C. In some embodiments, image 826 isdisplayed in response to activation 805 of shutter affordance 822 oractivation of input device 804, as described in reference to FIG. 8B.

Image 826 is one of the multiple still images captured as described inreference to FIG. 8B. While displaying image 826, device 800 detectsinput 811 at a location in image 826 corresponding to background object820 c. In response to input 811, device 800 displays an image (e.g.,image 828 shown in FIG. 8E) with background object 820 c displayedin-focus while foreground object 820 a continues to be displayedin-focus, as shown in FIG. 8E (e.g., tapping on another object in theimage causes an image to be displayed with that object in-focus and thepreviously selected object also in-focus, without capturing additionalimages).

As illustrated in FIG. 8E, image 828 is displayed in user interface 814.Image 828 includes foreground object 820 a and background object 820 cdisplayed in-focus, and middleground object 820 b displayedout-of-focus. Image 828 is displayed in response to input 811 on thelocation in image 824 corresponding to background object 820 c, asdescribed in reference to FIG. 8C. Input 811 is detected after anotherinput 809 selected foreground object 820 a to be displayed in-focus.Image 828 is a composite of a first image captured with foregroundobject 820 a in-focus and a second image captured with background object820 c in-focus. Both the first image and second image were captured inresponse to input 807 described in reference to FIG. 8B. The compositeimage 828 includes at least the foreground object 820 a from the firstimage and the background object 820 c from the second image. Otherportions of the composite image 828 (e.g., middleground object 820 b)can be from the first image, the second image, or from other capturedstill images, such that the other portions of image 828 are displayedout-of-focus.

In some embodiments, device 800 receives a request to display ananimation including two or more of the captured still images. Forexample, the animation includes displaying a first image (e.g., image824 shown in FIG. 8C) with a first focal plane for a predeterminedamount of time, followed by a second image (e.g., image 826 shown inFIG. 8D) with a different focal plane for a predetermined amount oftime. In some embodiments, the animation continues indefinitely, cyclingbetween the first image and the second image, until a cancellation inputis received. In some embodiments, the animation continues cyclingbetween the first image and the second image as long as an input ismaintained (e.g., as long as contact is detected on the touch-sensitivedisplay).

In some embodiments, device 800 determines depth information of thescene being captured in the multiple still images based on image data ofthe still images. For example, device identifies objects in the scene,and based on the focal planes of the objects, determines the depth ofthe object in the scene. In some embodiments, an operation is performedon at least one of the still images using the depth information, such asapplying a simulated depth effect (e.g., a visual effect having a depthcomponent), inserting an object into the scene, making a measurement,etc. In some embodiments, applying the simulated depth effect includesadjusting areas of the image that correspond to a selected depth to havedifferent degrees of blurriness/sharpness, sizes, degrees of brightness,degrees of saturation, and/or degrees of shape-distortion in order tosimulate the depth effect, such as a bokeh effect. In some embodiments,the simulated depth effect is “simulated” in that the effect is(artificially) generated based on a manipulation of the underlying imagedata for the area of the image to create and apply the effect to theimage (e.g., as opposed to being a “natural” effect that is based onunderlying data as originally captured via one or more cameras based onthe optical properties of light passing through one or more lenses toreach the image sensor of the camera).

FIG. 9 is a flow diagram illustrating a method for displaying capturinga plurality of still images with a plurality of different focal planes,in accordance with some embodiments. Method 900 is performed at a device(e.g., 100, 300, 500, 800) with a camera (e.g., 808). In someembodiments, the camera includes a single lens for adjusting the focallength of the camera. In some embodiments, the focal length changes bymodifying the shape of the lens. Some operations in method 900 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 900 provides, among other things, anintuitive way for capturing images of an environment with differentfocal planes. The method reduces the cognitive burden on a usercapturing an image of the environment, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to capture images with different focal planes faster andmore efficiently conserves power and increases the time between batterycharges.

The device (e.g., 800) detects (902) activation (e.g., 805, 807) of ashutter button (e.g., 804, 822, preview image 818) (e.g., a physical orvirtual shutter button) that is associated with capturing still images.

In response to the activation of the shutter button, the device captures(904) a plurality of still images with a plurality of different focalplanes. In some embodiments, at least one photographic property of thecamera (e.g., exposure, zoom level, white balance, contrast, ISO value)other than the focal plane is maintained during the capture of theplurality of still images.

Capturing the plurality of still images includes capturing (906) firstimage data with the camera focused at a first focal plane (e.g., theimage is captured with a lens of the camera set at a first focallength).

After capturing the first image data with the camera focused at thefirst focal plane, the device captures (908) second image data with thecamera focused at a second focal plane. The second focal plane isselected without reference to changes in objects in the field of view ofthe camera between the capture of the first image data and the captureof the second image data (e.g., the first focal plane and the secondfocal plane are predefined or are selected at the same time in responseto the activation of the shutter button and do not change based onmovement of the camera or movement of objects toward or away from thecamera between the capture of the first image data and the capture ofthe second image data). In some embodiments, the lens is changed to thesecond focal plane by modifying the shape of the lens. In someembodiments, the second image data is captured at a second time, laterthan a first time at which the first image data is captured. In someembodiments, the first image data and the second image data areconsolidated into a single data file. Capturing a plurality of stillimages with a plurality of different focal planes in response to asingle activation of a shutter button allows the still images to becaptured more efficiently. Performing an optimized operation withoutrequiring further user input enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, detecting the activation of the shutter buttonincludes detecting an input (e.g., 807) on a touch-sensitive display. Inresponse to detecting the input, the device selects a respective imageof the plurality of still images based on one or more properties of theinput and displays the respective image of the plurality of still images(e.g., a single finger contact triggers capture of the plurality ofstill images and selects the focal plane for an image to be displayed).In some embodiments, the one or properties of the input include acharacteristic intensity of the input. In some embodiments, the one ormore properties of the input (e.g., 807) includes a location (e.g., onmiddleground object 820 b) of the input on the touch-sensitive display.In some embodiments, if the input location corresponds to a location ofan object being captured in the plurality of still images (e.g., onmiddleground object 820 b), the focal plane of the image being displayedcorresponds to the focal plane of the object). Capturing a plurality ofstill images with a plurality of different focal planes and thendisplaying one of the still images in response to a single input allowsthe still images to be captured and displayed more efficiently.Performing an optimized operation without requiring further user inputenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

Optionally, after capturing the plurality of still images, the devicedisplays (910) on a touch-sensitive display (e.g., 802), a first image(e.g., 824) of the plurality of still images corresponding to the firstimage data. The device then detects (912) a first input (e.g., 809)(e.g., a finger contact) at a location (e.g., 820 a) on thetouch-sensitive display corresponding to the first image. In response tothe first input, the device displays (914) a second image (e.g., 826) ofthe plurality of still images corresponding to the second image data.Selecting a second image with a different focal plane for display basedon a single input on a touch-sensitive display allows the second imageto be displayed more efficiently. Performing an optimized operationwithout requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, displaying the second image (e.g., 826) includesselecting the second image from the plurality of still images based onone or properties of the first input, the one or more propertiesincluding a characteristic intensity of the first input. In someembodiments, in accordance with a determination that the characteristicintensity of the first input is greater than a threshold intensity, thedevice maintains display of the second image after the first inputceases to be detected by the device, and in accordance with adetermination that the characteristic intensity of the first input isless than the threshold intensity, the device displays the first imageafter the first input ceases to be detected by the device. In someembodiments, the threshold intensity is based at least in part on afocal plane of an object being captured in the plurality of still images(e.g., the characteristic intensity of input 809 pushes the focal planedeeper into image 824 until the focal plane is at a depth correspondingto an object in the image). In some embodiments, after changing to thefocal plane of the object, focus is maintained on the object forsubsequent activations of the shutter button. In some embodiments, inaccordance with the determination that the characteristic intensity ofthe first input is greater than the threshold intensity, the deviceprovides feedback indicating the threshold intensity is exceeded (e.g.,audio/tactile/visual feedback occurs when the characteristic intensityof the first input exceeds the threshold).

In some embodiments, the one or properties of the first input include aduration of the input (e.g., long press, short press).

In some embodiments, the one or more properties of the first inputincludes the location (e.g., on foreground object 820 a) of the firstinput on the touch-sensitive display. The device identifies an object inthe first image corresponding to the location of the first input, wherethe object is associated with a respective focal plane. The device thendisplays an image (e.g., 826) of the plurality of still images capturedwith the respective focal plane (e.g., when the input locationcorresponds to a location of an object being captured in the pluralityof still images, the focal plane changes to the respective focal planeof the object). In some embodiments, after the object is selected withthe first input, focus is maintained on the object for subsequentactivations of the shutter button.

In some embodiments, while displaying the second image (e.g., 826) ofthe plurality of still images, the device detects a second input (e.g.,811) (e.g., a finger contact) at a location (e.g., on background object820 c) on the touch-sensitive display corresponding to the second image.In response to the second input, the device displays a composite image(e.g., 828) on the touch-sensitive display. The composite image includesa portion of the second image associated with the first input (e.g., aportion of the image selected to be displayed in focus by the firstinput) and a portion of the second image associated with the secondinput (e.g., a portion of the image selected to be displayed in focus bythe second input, such that multiple planes (e.g., foreground andbackground) are displayed in-focus, while other planes (e.g., amiddleground) are displayed out-of-focus).

In some embodiments, after capturing the plurality of still images, thedevice receives a request (e.g., a single request, a single input) todisplay two or more images of the plurality of still images. In responseto receiving the request, the device displays a first image of theplurality of still images and displays a second image of the pluralityof still images a predetermined time after displaying the first image,where the first image and the second image were captured with differentfocal planes. In some embodiments, additional images having differentfocal depths are also displayed. In some embodiments, the sequence ofimages with different focal planes are automatically played through in aloop or back and forth (e.g., “boomerang”) animation. In someembodiments, the sequence of images is displayed in response to a userinput, and continues to be displayed either while the user's input ismaintained or until a cancellation input is received.

In some embodiments, the device determines depth information of a scenecaptured in the plurality of still images with the plurality ofdifferent focal planes. The depth information is determined based onimage data of the plurality of still images. In some embodiments, anoperation is performed on at least one of the plurality of still imagesusing the depth information, such as applying a simulated depth effect(e.g., a visual effect having a depth component), inserting an objectinto the scene, making a measurement, etc. In some embodiments, applyingthe simulated depth effect includes adjusting areas of the image thatcorrespond to a selected depth to have different degrees ofblurriness/sharpness, sizes, degrees of brightness, degrees ofsaturation, and/or degrees of shape-distortion in order to simulate thedepth effect, such as a bokeh effect. In some embodiments, the simulateddepth effect is “simulated” in that the effect is (artificially)generated based on a manipulation of the underlying image data for thearea of the image to create and apply the effect to the image (e.g., asopposed to being a “natural” effect that is based on underlying data asoriginally captured via one or more cameras based on the opticalproperties of light passing through one or more lenses to reach theimage sensor of the camera).

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9 ) are also applicable in an analogous manner tothe methods described above. For example, method 900 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 700. For example, a plurality of stillimages with a plurality of different focal planes as described abovewith respect to method 900 can used in a live communication sessiondescribed above with respect to method 700. For brevity, these detailsare not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to change thefocal plane of stored images or a live video communication. The presentdisclosure contemplates that in some instances, this gathered data mayinclude personal information data that uniquely identifies or can beused to contact or locate a specific person. Such personal informationdata can include demographic data, location-based data, telephonenumbers, email addresses, twitter IDs, home addresses, data or recordsrelating to a user's health or level of fitness (e.g., vital signsmeasurements, medication information, exercise information), date ofbirth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used to canbe used to recognize a person or subject within a captured image orvideo. Accordingly, use of such personal information data enables usersto more easily recognize the content of a captured image or live videocommunication. Further, other uses for personal information data thatbenefit the user are also contemplated by the present disclosure. Forinstance, health and fitness data may be used to provide insights into auser's general wellness, or may be used as positive feedback toindividuals using technology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof detection and recognition of a person or subject within an image orlive video communication, the present technology can be configured toallow users to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In addition to providing “opt in” and “opt out”options, the present disclosure contemplates providing notificationsrelating to the access or use of personal information. For instance, auser may be notified upon downloading an app that their personalinformation data will be accessed and then reminded again just beforepersonal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, images or livevideo communications can be displayed based on non-personal informationdata or a bare minimum amount of personal information, such as thecontent being requested by the device associated with a user, othernon-personal information available to the device, or publicly availableinformation.

What is claimed is:
 1. An electronic device, comprising: a camera; atouch-sensitive display; one or more processors; and memory storing oneor more programs configured to be executed by the one or moreprocessors, the one or more programs including instructions for:detecting activation of a shutter button that is associated withcapturing still images; in response to the activation of the shutterbutton, capturing a plurality of still images with a plurality ofdifferent focal planes, including: capturing first image data with thecamera focused at a first object in a first focal plane; and aftercapturing the first image data with the camera focused at the firstobject in the first focal plane, adjusting a camera focus from the firstfocal plane to a second focal plane and capturing second image data withthe camera focused at a second object in the second focal plane, whereinthe second focal plane is selected without reference to changes inobjects in the field of view of the camera between the capture of thefirst image data and the capture of the second image data; aftercapturing the plurality of still images, displaying, via thetouch-sensitive display, a first image of the plurality of still imagescorresponding to the first image data, wherein the first image includesthe first object in-focus and the second object out-of-focus; whiledisplaying the first image of the plurality of still images, detecting afirst input at a location on the touch-sensitive display correspondingto the location of the second object; and in response to detecting thefirst input, displaying, via the touch-sensitive display, a secondimage, wherein the second image includes the first object in-focus andthe second object in-focus.
 2. The electronic device of claim 1, the oneor more programs include instructions for: while displaying the firstimage of the plurality of still images, detecting a second input at alocation on the touch-sensitive display corresponding to the firstimage; and in response to detecting the second input, displaying, viathe touch-sensitive display, a third image of the plurality of stillimages corresponding to the second image data.
 3. The electronic deviceof claim 2, wherein displaying the third image includes selecting thethird image from the plurality of still images based on one or moreproperties of the second input, and wherein the one or more propertiesinclude a characteristic intensity of the second input.
 4. Theelectronic device of claim 3, the one or more programs includinginstructions for: in accordance with a determination that thecharacteristic intensity of the second input is greater than a thresholdintensity, maintaining display of the third image after the second inputceases to be detected by the device; and in accordance with adetermination that the characteristic intensity of the second input isless than the threshold intensity, displaying the first image after thesecond input ceases to be detected by the device.
 5. The electronicdevice of claim 4, wherein the threshold intensity is based at least inpart on a focal plane of an object being captured in the plurality ofstill images.
 6. The electronic device of claim 4, the one or moreprograms including instructions for: in accordance with thedetermination that the characteristic intensity of the second input isgreater than the threshold intensity, providing feedback indicating thethreshold intensity is exceeded.
 7. The electronic device of claim 2,wherein the one or more properties of the second input include aduration of the second input.
 8. The electronic device of claim 2,wherein the one or more properties of the second input includes thelocation of the second input on the touch-sensitive display, and whereinthe one or more programs include instructions for: identifying arespective object in the first image corresponding to the location ofthe second input, wherein the respective object is associated with arespective focal plane; and displaying an image of the plurality ofstill images captured with the respective focal plane.
 9. The electronicdevice of claim 1, wherein the second image is a composite image thatincludes a portion of the first image data and a portion of the secondimage data.
 10. The electronic device of claim 1, wherein at least onephotographic property of the camera other than the focal plane ismaintained during the capture of the plurality of still images.
 11. Theelectronic device of claim 1, wherein detecting the activation of theshutter button includes detecting an input corresponding to activationof the shutter button on the touch-sensitive display, and wherein theone or more programs include instructions for: in response to detectingthe input corresponding to activation of the shutter button: selecting arespective image of the plurality of still images based on one or moreproperties of the input corresponding to activation of the shutterbutton; and displaying, via the touch-sensitive display, the respectiveimage of the plurality of still images.
 12. The electronic device ofclaim 11, wherein the one or more properties of the input correspondingto activation of the shutter button include a characteristic intensityof the input.
 13. The electronic device of claim 11, wherein the one ormore properties of the input corresponding to activation of the shutterbutton includes a location of the input on the touch-sensitive display.14. The electronic device of claim 1, wherein the one or more programsinclude instructions for: after displaying the first image of theplurality of still images, displaying another image of the plurality ofstill images a predetermined time after displaying the first image,wherein the first image and the another image were captured withdifferent focal planes.
 15. The electronic device of claim 1, the one ormore programs including instructions for: determining depth informationof a scene captured in the plurality of still images with the pluralityof different focal planes, wherein the depth information is determinedbased on image data of the plurality of still images.
 16. Anon-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a camera and a touch-sensitive display, the oneor more programs including instructions for: detecting activation of ashutter button that is associated with capturing still images; inresponse to the activation of the shutter button, capturing a pluralityof still images with a plurality of different focal planes, including:capturing first image data with the camera focused at a first object ina first focal plane; and after capturing the first image data with thecamera focused at the first object in the first focal plane, adjusting acamera focus from the first focal plane to a second focal plane andcapturing second image data with the camera focused at a second objectin the second focal plane, wherein the second focal plane is selectedwithout reference to changes in objects in the field of view of thecamera between the capture of the first image data and the capture ofthe second image data; after capturing the plurality of still images,displaying, via the touch-sensitive display, a first image of theplurality of still images corresponding to the first image data, whereinthe first image includes the first object in-focus and the second objectout-of-focus; while displaying the first image of the plurality of stillimages, detecting a first input at a location on the touch-sensitivedisplay corresponding to the location of the second object; and inresponse to detecting the first input, displaying, via thetouch-sensitive display, a second image, wherein the second imageincludes the first object in-focus and the second object in-focus.
 17. Amethod comprising: at an electronic device with a camera and atouch-sensitive display: detecting activation of a shutter button thatis associated with capturing still images; in response to the activationof the shutter button, capturing a plurality of still images with aplurality of different focal planes, including: capturing first imagedata with the camera focused at a first object in a first focal plane;and after capturing the first image data with the camera focused at thefirst object in the first focal plane, adjusting a camera focus from thefirst focal plane to a second focal plane and capturing second imagedata with the camera focused at a second object in the second focalplane, wherein the second focal plane is selected without reference tochanges in objects in the field of view of the camera between thecapture of the first image data and the capture of the second imagedata; after capturing the plurality of still images, displaying, via thetouch-sensitive display, a first image of the plurality of still imagescorresponding to the first image data, wherein the first image includesthe first object in-focus and the second object out-of-focus; whiledisplaying the first image of the plurality of still images, detecting afirst input at a location on the touch-sensitive display correspondingto the location of the second object; and in response to detecting thefirst input, displaying, via the touch-sensitive display, a secondimage, wherein the second image includes the first object in-focus andthe second object in-focus.
 18. The electronic device of claim 1, theone or more programs include instructions for: after capturing theplurality of still images, displaying, via the touch-sensitive display,the first image of the plurality of still images corresponding to thefirst image data without displaying other images of the plurality ofstill images.
 19. The electronic device of claim 1, the one or moreprograms including instructions for: in response to detecting the firstinput, displaying, via the touch-sensitive display, the second imagewithout displaying other images of the plurality of still images. 20.The non-transitory computer-readable storage medium of claim 16, the oneor more programs include instructions for: while displaying the firstimage of the plurality of still images, detecting a second input at alocation on the touch-sensitive display corresponding to the firstimage; and in response to detecting the second input, displaying, viathe touch-sensitive display, a third image of the plurality of stillimages corresponding to the second image data.
 21. The non-transitorycomputer-readable storage medium of claim 20, wherein displaying thethird image includes selecting the third image from the plurality ofstill images based on one or more properties of the second input, andwherein the one or more properties include a characteristic intensity ofthe second input.
 22. The non-transitory computer-readable storagemedium of claim 21, the one or more programs including instructions for:in accordance with a determination that the characteristic intensity ofthe second input is greater than a threshold intensity, maintainingdisplay of the third image after the second input ceases to be detectedby the device; and in accordance with a determination that thecharacteristic intensity of the second input is less than the thresholdintensity, displaying the first image after the second input ceases tobe detected by the device.
 23. The non-transitory computer-readablestorage medium of claim 22, wherein the threshold intensity is based atleast in part on a focal plane of an object being captured in theplurality of still images.
 24. The non-transitory computer-readablestorage medium of claim 22, the one or more programs includinginstructions for: in accordance with the determination that thecharacteristic intensity of the second input is greater than thethreshold intensity, providing feedback indicating the thresholdintensity is exceeded.
 25. The non-transitory computer-readable storagemedium of claim 20, wherein the one or more properties of the secondinput include a duration of the second input.
 26. The non-transitorycomputer-readable storage medium of claim 20, wherein the one or moreproperties of the second input includes the location of the second inputon the touch-sensitive display, and wherein the one or more programsinclude instructions for: identifying a respective object in the firstimage corresponding to the location of the second input, wherein therespective object is associated with a respective focal plane; anddisplaying an image of the plurality of still images captured with therespective focal plane.
 27. The non-transitory computer-readable storagemedium of claim 16, wherein the second image is a composite image thatincludes a portion of the first image data and a portion of the secondimage data.
 28. The non-transitory computer-readable storage medium ofclaim 16, wherein at least one photographic property of the camera otherthan the focal plane is maintained during the capture of the pluralityof still images.
 29. The non-transitory computer-readable storage mediumof claim 16, wherein detecting the activation of the shutter buttonincludes detecting an input corresponding to activation of the shutterbutton on the touch-sensitive display, and wherein the one or moreprograms include instructions for: in response to detecting the inputcorresponding to activation of the shutter button: selecting arespective image of the plurality of still images based on one or moreproperties of the input corresponding to activation of the shutterbutton; and displaying, via the touch-sensitive display, the respectiveimage of the plurality of still images.
 30. The non-transitorycomputer-readable storage medium of claim 29, wherein the one or moreproperties of the input corresponding to activation of the shutterbutton include a characteristic intensity of the input.
 31. Thenon-transitory computer-readable storage medium of claim 29, wherein theone or more properties of the input corresponding to activation of theshutter button includes a location of the input on the touch-sensitivedisplay.
 32. The non-transitory computer-readable storage medium ofclaim 16, wherein the one or more programs include instructions for:after displaying the first image of the plurality of still images,displaying another image of the plurality of still images apredetermined time after displaying the first image, wherein the firstimage and the another image were captured with different focal planes.33. The non-transitory computer-readable storage medium of claim 16, theone or more programs including instructions for: determining depthinformation of a scene captured in the plurality of still images withthe plurality of different focal planes, wherein the depth informationis determined based on image data of the plurality of still images. 34.The non-transitory computer-readable storage medium of claim 16, the oneor more programs include instructions for: after capturing the pluralityof still images, displaying, via the touch-sensitive display, the firstimage of the plurality of still images corresponding to the first imagedata without displaying other images of the plurality of still images.35. The non-transitory computer-readable storage medium of claim 16, theone or more programs including instructions for: in response todetecting the first input, displaying, via the touch-sensitive display,the second image without displaying other images of the plurality ofstill images.
 36. The method of claim 17, wherein the method furthercomprises: while displaying the first image of the plurality of stillimages, detecting a second input at a location on the touch-sensitivedisplay corresponding to the first image; and in response to detectingthe second input, displaying, via the touch-sensitive display, a thirdimage of the plurality of still images corresponding to the second imagedata.
 37. The method of claim 36, wherein displaying the third imageincludes selecting the third image from the plurality of still imagesbased on one or more properties of the second input, and wherein the oneor more properties include a characteristic intensity of the secondinput.
 38. The method of claim 37, further comprising: in accordancewith a determination that the characteristic intensity of the secondinput is greater than a threshold intensity, maintaining display of thethird image after the second input ceases to be detected by the device;and in accordance with a determination that the characteristic intensityof the second input is less than the threshold intensity, displaying thefirst image after the second input ceases to be detected by the device.39. The method of claim 38, wherein the threshold intensity is based atleast in part on a focal plane of an object being captured in theplurality of still images.
 40. The method of claim 38, furthercomprising: in accordance with the determination that the characteristicintensity of the second input is greater than the threshold intensity,providing feedback indicating the threshold intensity is exceeded. 41.The method of claim 36, wherein the one or more properties of the secondinput include a duration of the second input.
 42. The method of claim36, wherein the one or more properties of the second input includes thelocation of the second input on the touch-sensitive display, and whereinthe method further comprises: identifying a respective object in thefirst image corresponding to the location of the second input, whereinthe respective object is associated with a respective focal plane; anddisplaying an image of the plurality of still images captured with therespective focal plane.
 43. The method of claim 36, wherein the secondimage is a composite image that includes a portion of the first imagedata and a portion of the second image data.
 44. The method of claim 17,wherein at least one photographic property of the camera other than thefocal plane is maintained during the capture of the plurality of stillimages.
 45. The method of claim 17, wherein detecting the activation ofthe shutter button includes detecting an input corresponding toactivation of the shutter button on the touch-sensitive display, andwherein the method further comprises: in response to detecting the inputcorresponding to activation of the shutter button: selecting arespective image of the plurality of still images based on one or moreproperties of the input corresponding to activation of the shutterbutton; and displaying, via the touch-sensitive display, the respectiveimage of the plurality of still images.
 46. The method of claim 45,wherein the one or more properties of the input corresponding toactivation of the shutter button include a characteristic intensity ofthe input.
 47. The method of claim 45, wherein the one or moreproperties of the input corresponding to activation of the shutterbutton includes a location of the input on the touch-sensitive display.48. The method of claim 17, wherein the method further comprises: afterdisplaying the first image of the plurality of still images, displayinganother image of the plurality of still images a predetermined timeafter displaying the first image, wherein the first image and theanother image were captured with different focal planes.
 49. The methodof claim 17, further comprising: determining depth information of ascene captured in the plurality of still images with the plurality ofdifferent focal planes, wherein the depth information is determinedbased on image data of the plurality of still images.
 50. The method ofclaim 17, wherein the method further comprises: after capturing theplurality of still images, displaying, via the touch-sensitive display,the first image of the plurality of still images corresponding to thefirst image data without displaying other images of the plurality ofstill images.
 51. The method of claim 17, further comprising: inresponse to detecting the first input, displaying, via thetouch-sensitive display, the second image without displaying otherimages of the plurality of still images.